CiscoISE-SuspendGuestUser

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Content Index

When a new sentinel incident is created, this playbook gets triggered and performs the following actions: 1. For each Account in the incident suspends user in Cisco ISE by its name. 2. Adds comment to the incident with information about suspended users.

Attribute Value
Type Playbook
Solution Cisco ISE
Source View on GitHub

Logic App Connectors

This playbook uses 2 Logic App connectors / built-in actions:

Connector / Action Type Connections Actions
azuresentinel Managed 1 2
CiscoISE Custom 1 1
Action parameters (URLs, paths, function IDs)

azuresentinel (Managed)

Action Method Endpoint Other
Add_comment_to_incident_(V3) post /Incidents/Comment —
Entities_-_Get_Accounts post /entities/account —

CiscoISE (Custom)

Action Method Endpoint Other
Suspend_guest_user_by_name put /ers/config/guestuser/suspend/name/@{encodeURIComponent(item()['Name'])} —

Additional Documentation

📄 Source: CiscoISE-SuspendGuestUser/readme.md

Summary

When a new sentinel incident is created, this playbook gets triggered and performs the following actions:

  1. For each Account in the incident suspends user in Cisco ISE by its name.
  2. Adds comment to the incident with information about suspended users.


Prerequisites

  1. Prior to the deployment of this playbook, Cisco ISE Connector needs to be deployed under the same subscription.
  2. Obtain Cisco ISE ERS API credentials. Refer to Cisco ISE Custom Connector documentation.

Deployment instructions

  1. To deploy the Playbook, click the Deploy to Azure button. This will launch the ARM Template deployment wizard.
  2. Fill in the required paramteres:
    • Playbook Name: Enter the playbook name here

Deploy to Azure Deploy to Azure

Post-Deployment instructions

a. Authorize connections

Once deployment is complete, authorize each connection.

  1. Click the Azure Sentinel connection resource
  2. Click edit API connection
  3. Click Authorize
  4. Sign in
  5. Click Save
  6. Repeat steps for other connections

b. Configurations in Sentinel

  1. In Azure sentinel, analytical rules have to be configured to trigger an incident with risky user account. In the Entity maping section of the analytics rule creation workflow, user's name has to be mapped to Name identitfier of the Account entity type. Check the documentation to learn more about mapping entities.
  2. Configure the automation rules to trigger the playbook.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Playbooks · Back to Cisco ISE